Update JavaFX wizard names and move DukeScript wizard to a better position. #6551
Conversation
mbien
commented
Oct 10, 2023
•
mbien
commented
- Its now closer to other frontend templates, like JavaFX, and has a more specific name
- Remove the "(Gluon)" postfix from the JavaFX templates since they don't seem to use anything from gluon
mbien
added
the
Java
Its now closer to other frontend templates, like JavaFX, and has a more specific name. Remove the "(Gluon)" postfix from the JavaFX templates since they don't seem to use anything from gluon.
mbien
force-pushed
the
update-dukescript-wizard-category
branch
from
d58bdb3 to
f384c5b
Compare
mbien
changed the title
There was a problem hiding this comment.
Thanks! Better than nothing - in some ways I'd prefer to remove it entirely.
Should it be Dukescript or Apache NetBeans HTML/Java API ? Mind you development of this seems to have stalled(?) and the build job has been failing for ages - https://github.com/apache/netbeans-html4j
|
i mean I have nothing against removing the dukescript pieces. If the embedded browser isn't used anywhere it might even allow NB to drop bundled javafx (which is a fairly large dependency). The main reason I renamed it was because I end up in that wizard from time to time by accident, then realizing that its clearly not what I expected it to be. thanks for taking a look -> merging |
Well, we don't bundle it, and the web view we never could as it's LGPL. All uses need to remain optional, so this wizard should really drop back to displaying something useful when its dependency cannot be met. Still, discussion for elsewhere. Thanks for the change. Have had multiple discussions with end users ending up in that wizard also by accident! |
